-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validator historical state restoration #922
Conversation
3b4a7fe
to
89738ff
Compare
9e9882b
to
6879c27
Compare
fc34613
to
1459644
Compare
92b6e96
to
7b20c4b
Compare
77fcad2
to
4df6a21
Compare
7e06bd8
to
165d514
Compare
The reason for occasional integration tests failure on Windows is described in codex-storage/nim-ethers#79. |
98e3378
to
a91c76f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work, Marcin, thank you. It took me quite a few hours to review this PR. In the future, any kind of split up of the work (into separate PRs) would be much appreciated!
…en `BlockTag.pending` is requested.
0a30384
to
a43e1e0
Compare
At the moment the validator has started, there may already be existing active storage requests containing slots with slot ids that should be monitored by the validator: these are slot ids that either belong to the group observed by the validator or basically any slot id if validator is to monitor the whole slot id space.
In this context we want the validator to find and monitor all those slots id associated with storage requests that started earlier and have not yet concluded.
For more details, please refer to the discussion in #458.